Skip to content

Fix v_num formatting for RichProgressBar #21040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Aug 8, 2025
Merged

Fix v_num formatting for RichProgressBar #21040

merged 3 commits into from
Aug 8, 2025

Conversation

SkafteNicki
Copy link
Collaborator

@SkafteNicki SkafteNicki commented Aug 8, 2025 •
edited by github-actions bot
Loading

What does this PR do?

Fixes #20268
Minor consistency issue. For RichProgressBar the v_num experiment indicator is currently showing up as 0.000, 1.000 etc. due this being interpret as a metric and then the default metric formatting is applied

pytorch-lightning/src/lightning/pytorch/callbacks/progress/rich_progress.py

Line 219 in 791753b

metrics_format: str = ".3f"

PR makes the change that the format is only applied to floats and not ints, which would fix this.
This somewhat is consistent with the TQDM progress bar which also includes int from formatting (padding)

pytorch-lightning/src/lightning/pytorch/callbacks/progress/tqdm_progress.py

Line 49 in 791753b

should_be_padded = isinstance(n, (float, str))

Before submitting
  • Was this discussed/agreed via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist
  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--21040.org.readthedocs.build/en/21040/

@github-actions github-actions bot added the pl Generic label for PyTorch Lightning package label Aug 8, 2025
@Borda Borda merged commit ce038e8 into Lightning-AI:master Aug 8, 2025
83 checks passed
Borda pushed a commit that referenced this pull request Aug 13, 2025
@SkafteNicki @Borda
Fix v_num formatting for RichProgressBar (#21040)
5d55306 
(cherry picked from commit ce038e8)
Borda pushed a commit that referenced this pull request Aug 13, 2025
@SkafteNicki @Borda
Fix v_num formatting for RichProgressBar (#21040)
4c66b9c 
(cherry picked from commit ce038e8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Borda Borda Borda approved these changes

@justusschock justusschock justusschock approved these changes

@lantiga lantiga Awaiting requested review from lantiga lantiga is a code owner

@tchaton tchaton Awaiting requested review from tchaton tchaton is a code owner

@ethanwharris ethanwharris Awaiting requested review from ethanwharris ethanwharris is a code owner

Assignees

No one assigned

Labels

pl Generic label for PyTorch Lightning package

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

rich progress bar shows v_num as 0.000

3 participants

@SkafteNicki @Borda @justusschock